CheckoutSessions — top level Setup Future Usage#6292
CheckoutSessions — top level Setup Future Usage#6292gbirch-stripe wants to merge 6 commits intomasterfrom
Conversation
| func setupFutureUsage(for paymentMethodType: STPPaymentMethodType) -> String? { | ||
| _ = paymentMethodType | ||
| return setupFutureUsage | ||
| } |
There was a problem hiding this comment.
PMO SFU logic will go here
StripeConnectSPI API-@_exported @_spi(DashboardOnly) @_spi(STP) import StripeCore
+@_exported @_spi(STP) @_spi(DashboardOnly) import StripeCoreIf you are adding a new public API consider the following:
If you are modifying or removing a public API:
If you confirm these APIs need to be added/updated and have undergone necessary review, add the label ℹ️ If this comment appears to be left in error, make sure your branch is up-to-date with |
|
verify public interface is acting up 😞 . verified that no public api changes are being made |
porter-stripe
left a comment
porter-stripe
left a comment
There was a problem hiding this comment.
looks good one question
| XCTAssertFalse(session.merchantWillSavePaymentMethod(.card)) | ||
| } | ||
|
|
||
| func testMerchantWillSavePaymentMethod_paymentModeWithTopLevelSetupFutureUsage() { |
There was a problem hiding this comment.
Is it worth adding a test for none setup_future_usage value?
2 participants
Summary
Implement top level SFU. PMO SFU in subsequent PR
Motivation
https://docs.google.com/document/d/1CWglcOHR6I8cOWKjztPfnhnVG8axucpv-j5cWIoey7E/edit?pli=1&tab=t.g4karprubz63#heading=h.qr0ujyg56e8u
Testing
Changelog